• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    DETERMINING THE APPROPRIATE RADIO RESOURCE TO BE REQUESTED IN THE EVENT OF A SWITCHED FAULT RECOVERY PROCEDURE. A system and method for implementing disaster recovery in a wireless device for circuit-switched disaster recovery of a first network that does not provide a circuit-switched domain service is presented. A radio call message is received from the first network. The radio call message instructs the wireless device to implement circuit-switched disaster recovery for a circuit-switched network. The radio call message is inspected for information indicative of a service associated with the radio call message, and a suitable channel type for the service is determined from information indicative of the service. A message requesting to initiate the establishment of a radio connection is transmitted. The request message identifies the proper channel type, and the service is used in the circuit-switched network.
    公开号:BR112012010965B1
    申请号:R112012010965-0
    申请日:2010-11-08
    公开日:2021-08-03
    发明作者:Rene Faurie；Claude Jean-Frederic Arzelier
    申请人:Blackberry Limited；
    IPC主号:
    专利说明:

    CROSS REFERENCE TO RELATED APPLICATIONS
    This application claims priority and incorporates by reference European Patent Application number 09306075.4 entitled "Determination of Appropriate Radio Resource to be Requested in Case of a Circuit-Switched (CS) Fallback Procedure" Requested in Case of a Circuit Switched (CS) Disaster Recovery Procedure”, required November 9, 2009. HISTORIC
    The present disclosure relates generally to systems and methods for communication between a wireless device or user agent (UA) and a network, and more particularly to systems and methods for coordinating communication resources between wireless devices and networks including circuit switched networks.
    As used herein, the term "user agent" or UA may refer to wireless devices such as mobile phones, personal digital assistants (PDAs), handheld or laptop computers, and similar devices, including mobile stations (MS) or user equipment (UE) that may have telecommunication capabilities. In some versions, the UA may refer to a wireless, mobile device. The term “UA” may also refer to devices that have similar capabilities but are not generically transportable, such as desktop computers, desktop boxes, or network nodes.
    The UA may operate on a wireless communication network that provides high speed data and/or voice communication. Wireless communication networks may implement circuit-switched (CS) and/or packet-switched (CS) communication protocols to provide various services. For example, the UA may operate under one or more of an Enhanced Universal Terrestrial Radio Access Network (E-UTRAN), Universal Terrestrial Radio Access Network (UTRAN) Universal), Global System for Mobile Communications (GSM), Evolution-Data Optimized (EV-DO), Digital Enhanced Cordless Telecommunications (DECT), Digital AMPS ( IS-136/TDMA), Integrated Digital Enhanced Network (DEN), Universal Mobile Telecommunications System (UMTS), Enhanced Data Rates for GSM Evolution (EDGE) Enhanced Data Rates for GSM Evolution ), GPRS/EDGE Radio Access Network (GERAN - GPRS/EDGE Radio Access Network) and General Packet Radio Service (GBPRS - General Packet Radio Service) . Other wireless networks that UAs may operate on include, but are not limited to, Code Division Multiple Access (CDMA), cdma2000, cdma2000 IxRTT, cdma2000 HRPD, WLAN (for example, IEEE 802.11) and WRAN (eg IEEE 802.22). UAs will also be able to operate in fixed network environments such as Digital Subscriber Line (xDSL - Digital Subscriber Line) environments, Data cable networks
    Over Cable Service Interface Specification (DOCSIS Data over Data Cable Service Interface Specification), Wireless Personal Area Networks (PAN), Bluetooth, ZigBee, Wireless Metropolitan Area Networks (MAN). Wireless) (eg WIMAN, IEEE 802.20, IEEE 802.22 Ethernet) or optical networks. Some UAs may be capable of multimode operation in that they can operate on more than one access network technology, either on a single access network at a time or, on some devices, using multiple access technologies simultaneously.
    In wireless telecommunications systems, transmission equipment at a base station transmits signals across a geographic region known as a cell. With the evolution of technology, more advanced equipment was being introduced that could provide services that were not possible before. This advanced equipment may include, for example, an evolved universal terrestrial radio access network (E-UTRAN) Node B (eNB) instead of a base station or other systems and devices that are more highly evolved than the equivalent equipment in a traditional wireless telecommunication system. Such advanced or next-generation equipment may be referred to herein as long-term evolution equipment (LTE), and a packet-based network using such equipment may be referred to as an evolved packet system (EPS). As used herein, the term "access device" will refer to any component, such as a traditional base station, eNB or other LTE access device, that can provide the UA with access to other components in a telecommunication system.
    The different networks described above provide varied services for connected UAs. Some networks, for example, provide only PS services and cannot provide CS voice or other services in the CS domain. As such, the UA can be configured to connect to multiple network types to access both PS and CS domain services. For example, if the UA is connected to a first network cell that does not provide services in the CS domain, the UA can be configured to implement a disaster recovery procedure, which may be referred to here as "CS recovery", to connect to an accessible network such as a GERAN network or Universal Terrestrial Radio Access Network (UTRAN) to access the voice or other services in the CS domain provided by these networks. As such, the CS disaster recovery procedure allows the UA connected to a network that uses a first radio access technology (RAT) and that only provides services in the PS domain, to connect with another network that provides services in the CS domain. CS recovery can be used, for example, to initiate voice calls through a cell of a network that provides services in the CS domain when, at the time of initiating the voice call, the UA was associated with a cell of a network that only provides services in the PS domain. The UA that initiates the voice call may be either idle or connected (eg, active) in the cell of the network that only provides services in the PS domain. In case the UA is idle, it can be said to be camped in the cell and could be monitoring the radio call channel of that cell by radio call messages for sessions or mobile terminated calls. In case the UA is connected, it could be communicating with the cell and transferring data to a service in the PS domain.
    Turning to Figure 1, an exemplary CS disaster recovery process is illustrated, whereby the UA 10 switches from an E-UTRAN network cell 12 to a GERAN or UTRAN cell 14 to access services in the CS domain to initiate a call to voice. As will be described, to facilitate CS recovery, the UA 10 may be configured to communicate with both PS-based and CS-based networks. For example, the UA 10 may support combined procedures for posting EPS/International Mobile Subscriber Identity (MSI-EPS/International Mobile Subscriber Identity), and updating Tracking Area to register with a Mobility Management Entity (MME). Mobility Management Entity) to access services in the PS domain (eg via an E-UTRAN, UTRAN or GERAN access network) and register with the Mobile Switching Center (MSC ~ Mobile Switching Center) to access services in the domain CS (for example, through a UTRAN or GERAN access network or another network that supports services in the CS domain). The combined procedures also allow the MSC and MME to create an association between each other so that each is aware that the UA 10 is registered simultaneously with both the MSC and the MME and that therefore the UA 10 is registered with both the PS network as with the CS network.
    Figure 2 is a data flow diagram illustrating an exemplary data flow for a mobile terminated CS recovery procedure where the UA 10 in connected mode is redirected to GERAN or UTRAN. In Figure 1, the UA 10 is initially connected to the E-UTRAN cell 12. Since the E-UTRAN cell 12 does not provide services in the CS domain, the UA 10 implements CS retrieval to communicate with the GERAN or UTRAN cell 14 to access services in the CS domain they provide.
    By way of example, a network-aided cell (NACC) change related to a mobile-originated voice call will be described. Referring to Figures 1 and 2, the exemplary process is initiated by an MSC 16 sending a CS radio call to an MME 20 which, in turn, directs the MME 20 to send a CS service notification radio call 22 to the UA 10. In Figure 1, communications from E-UTRAN cell 12 are indicated by arrow 23 and communications from UA 10 to E-UTRAN cell 12 are indicated by arrow 25. In CS service 22, the UA 10 sends an Extended service request 24 to the eNB 26 of the E-UTRAN cell 12. However, the E-UTRAN cell is not configured to provide services in the CS domain. Thus, the MME 20 sends an SI Application Protocol (SI-AP) message with a CS recovery indicator 30 to the eNB 26.
    To narrow down the exemplary data stream, Figure 2 indicates some data streams by boxes, such as the optional measurement report 32 that may be provided by the UA 10 to indicate information such as signal strength and the like of neighboring cells to which it may be designated. That is, when performing CS recovery, the UA 10 may be in the best position to determine which cell or cells are candidate cells on which to recover. As such, the UA 10 can detect which cells are close together or have a particularly strong received signal strength or quality (or other such parameter), and thus with which cells the UA would likely have a successful connection following the CS recovery process. Then, during the CS recovery process, the UA 10 may perform a measurement step to detect and identify the accessible cells for the UA 10. In other words, before recovering to a cell that provides services in the CS domain, the UA 10 will be able to search for available candidate network cells through a measurement process.
    The eNodeB (eNB) may trigger an inter-RAT cell change order, optionally with a NACC signal 34 which is sent to the UA 10, alternatively with a connection release with redirection is signaled 3 6. The eNB 2 6 indicates, according to SI-AP, a request to release the UA context 3 8 to the MME 20. Thereafter, the release of the SI UA context, the location area (LA) update, the combined routing area update occurs (RA)/LA, RA update, or LA update and RA update 42 take place in the new GERAN or UTRAN cell. If the target RAT is GERAN, suspension of PS services can occur if the new cell or UA does not support concurrent CS and PS services. In this case, a suspend message 44 is sent from the UA 10 to the base station system (BSS) 46, which is then communicated from the BSS 46 to a server node GPRS (general packet radio service) Support Node (SGSN) 48. Thereafter, the suspend request/response 50 is communicated between the SGSN 48 and the MME 20 and a bearer update (ES) 52 occurs between the MME 20 and a serving gateway (S-GW) 54.
    The UA 10 signals a radio call response 56 to the BSS/RNS 46 which, in turn, forwards the radio call response to the MSC 16. If CS recovery implies a change in MSC 16, additional steps may be performed, as indicated in box 58, such as communicating a connection rejection 60 from MSC 16 to BSS/RNS 46, communicating connection release 62 from BSS/RNS 46 to UA 10, and an LA update or RA update/ Combined LA 64. Finally, the CS 66 call establishment procedure occurs, such that, as indicated in Figure 1, the UA 10 can move, as indicated by arrow 68, from communicating with the E-UTRAN cell 12 to communicate, as indicated by arrow 70, with the GERAN or UTRAN cell 14 over a CS channel.
    When implementing CS recovery, delay can be a concern. If the UA 10 is initially camped in cell E-UTRAN 12 and wishes to access services in the CS domain in cell GERAN or UTRAN 14, a CS recovery process can be performed. Although the procedure for establishing the radio resource control (RRC) connection of the CS recovery process may be relatively short (eg around 150 ms is the target time for the E-UTRA system design), measurement steps and a step to select the target cell for services in the CS domain can potentially take a significant amount of time. As such, CS recovery may be delayed resulting in delays in the establishment of services in the CS domain, possibly delaying the establishment of a connection for the user or negatively affecting other services accessed by the UA 10.
    In addition to this potential for the user to experience a noticeable delay in services, CS RECOVERY can result in inefficient or inappropriate use of network resources. For example, the UA is radio-called in a GERAN or UTRAN network for a move1 terminating call, some information is communicated by the network in the radio-call message. That is, the radio call message may provide an indication of the service for which the UA is radio called, or an indication of the type of radio channel appropriate to support the service. Similarly, in the case of a mobile-originated call (MO), the UA is indicating to the network a cause of establishment that reflects the service or type of channel requested. Thus, the network can reasonably allocate appropriate channels for the desired communication.
    However, this information is either not available on the E-UTRAN interfaces used when starting the CS recovery procedure, or it is available but not evaluated to request the allocation of radio channels in GERAN, UTRAN or E-UTRAN. As a consequence, the network may decide to allocate non-optimal resources, such as a signaling channel to serve a voice call, which can affect CS recovery performance, or a traffic channel to serve a signaling procedure, causing loss. of the radio feature.
    Thus, systems and methods that address the issues listed above and allow the establishment and utilization of optimal resources by CS retrieval would provide a useful improvement in the technology. BRIEF DESCRIPTION OF THE DRAWINGS
    In the accompanying drawings, reference numerals represent like parts or operations.
    Figure 1 is an illustration of an exemplary CS retrieval process in which the UE passes from an E-UTRAN cell to a GERAN or UTRAN cell to access services in the CS domain to initiate a voice call.
    Figure 2 is a data flow diagram illustrating an exemplary data flow for a mobile terminated CS recovery procedure where the UA in connected mode is redirected to GERAN or UTRAN without PS Transfer.
    Figure 3 is a data flow diagram illustrating the initiation of an exemplary mobile termination call in a GERAN network where the UA is in idle mode.
    Figure 4 is a data flow diagram illustrating mobile termination call initiation in an UTRAN network where the UA is in idle mode.
    Figure 5 is a data flow diagram illustrating the CS recovery procedure of mobile origination with Packet Switched Transfer initiated in an E-UTRAN network,
    Figure 6 is an illustration of the data flow for implementing a CS Mobile Termination retrieval where service-related information is passed to the UA in idle mode within a radio call message.
    Figure 7 shows a block diagram of the user equipment (UA).
    Figure 8 illustrates a software environment that can be implemented by a user equipment processor.
    Figure 9 illustrates an example of a system that includes a processing component suitable for implementing a method to provide continuity for sessions that change across networks. DETAILED DESCRIPTION
    The present disclosure provides a system and method for circuit-switched (CS) recovery and, specifically, to minimize delay, optimize radio resource allocation, and improve reliability for CS recovery.
    One version of the invention includes a method of implementing recovery in a wireless device for circuit-switched recovery of a first network that does not provide service in the circuit-switched domain. The radio call message instructs the wireless device to implement circuit-switched recovery in a circuit-switched network. The method includes inspecting the radio call message for information indicative of a service associated with the radio call message, determining from the information indicative of the service a suitable channel type for the service, and transmitting a request message to initiate establishment of a radio connection. The request message identifies the proper channel type. The method includes using the service on the circuit switched network.
    Other versions include a wireless device configured to perform circuit-switched recovery of a first network that does not provide a service in the circuit-switched domain including a processor configured to construct a service request message. The service request message identifies the cause for the circuit-switched (CS) service to be provided by a circuit-switched network. The processor is configured to transmit the service request message to the first network. The service request message initiates a recovery procedure. The processor is configured to establish a connection to the circuit-switched network, and use the CS service in the circuit-switched network.
    Other versions include a wireless device configured to perform circuit-switched recovery of a first network that does not provide service in the circuit-switched domain including a processor configured to receive a radio call message from the first network. The radio call message instructs the wireless device to implement circuit-switched recovery to a circuit-switched network. The processor is configured to inspect the radio call message for information indicative of a service associated with the radio call message, determine from the information indicative of the service a suitable channel type for the service, and transmit a request message to initiate the establishment of a radio connection. The request message identifies the proper channel type. The processor is configured to use the service in the circuit switched network.
    The various aspects of the disclosure are now described with reference to the accompanying drawings, in which numbers refer, as a whole, to corresponding or like elements. However, it should be understood that the drawings and detailed description related thereto are not intended to limit the claimed topic to the particular form disclosed. Rather, the intent is to cover all modifications, equivalents, and alternatives that fall within the spirit and scope of the claimed topic.
    As used herein, the terms "component", "system", and the like are intended to refer to a computer-related entity, whether hardware, a combination of hardware and software, or running software. For example, a component may be, but is not limited to, a process that runs on a processor, a processor, an object, an executable, an execution thread, a program, and/or a computer. By way of illustration, both the application that processes on a computer and the computer can be a component. One or more components may reside within a process and/or thread of execution and the component may be located on one computer and/or distributed between two or more computers.
    The word "exemplary" is used herein to mean to serve as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be interpreted as preferred or advantageous over other aspects or designs.
    Furthermore, the disclosed topic may be implemented as a system, method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control the computer-based device or on the processor to define aspects detailed here. The term "article of manufacture" (or alternatively, "computer program product") as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier or media. For example, computer readable media may include, but are not limited to, magnetic storage devices (eg, hard disk, floppy disk, magnetic strips, and the like), optical disks (eg, compact disk (CD), digital versatile disk (DVD), and the like), smart cards, and flash memory devices (eg, card strip and the like) . Additionally, it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used to transmit and receive electronic mail or in accessing a network such as the Internet or a local area network (LAN). Naturally, those skilled in the technology will recognize that many indications can be made to the configuration without deviating from the scope or spirit of the claimed topic.
    As stated above, there is the potential for CS recovery to cause non-optimal resource allocation, such as a signaling channel to service a voice call, which can create situations that affect CS recovery performance, or the traffic channel to serve the signaling procedure, causing the loss of radio resources. For example, turning to Figure 3, in the case of a mobile termination call initiation in GERAN, the UA 10 is typically provided with the indication "Channel Needed" in a radio call message 72 sent by the GERAN network 74, which is information that signals the most suitable radio channel to support the service for which the UA is radio-called, for example, the Stand Alone Dedicated Control Channel (SDCCH) signaling channel, traffic channel ( TCH/full(F) The UA 10 then sends an appropriate channel request 76 to the GERAN network 74 taking into account the "Paging Indication" of the "Channel Needed" element received in the radio call message 72 and the capacity of the UA 10 (full rate only, dual rate only, SDCCH only), which allows the BSS to grant the most desirable channel. For example, Table 1 below lists the channel request messages when answering a radio call for establishing a RR connection.

    However, in the case of the UA radio call in E-UTRAN for a CS repair termination session, the radio call (CS service notification) is sent by the MME 20, as described with respect to Figure 2, to the UA 10 in source network connected mode (packet only) does not contain any "Paging Indication" information. This radio call notification may include information about the service to which the mobile station is radio call (e.g., Supplementary Service code, location service indicator (LCS)). In case the radio call is made to reach the UA 10 in idle mode (see, for example, Figure 6), the radio call messages sent on the SI interface and on the radio interface do not even contain any indication of the service to which the mobile station is radio-calling. Furthermore, the GERAN RR protocol does not specify how the UA should construct the Channel Request when responding to the call when triggered by the CS recovery procedure. This means that the existing channel request procedure defined for GERAN is not applicable as such for CS (lack of "Paging Indication") retrieval to determine the appropriate and optimal information in the channel request message that can be sent on the target network .
    As a result, CS recovery in GERAN could lead to inconsistent UA implementations, for example, inappropriate channel type request to the service being activated, resulting in exhaustion of allocated resources or a longer establishment time. In particular, the request and initial allocation of an SDCCH in the case of voice call establishment will delay the establishment of the voice path compared to the case where the traffic channel (TCH) is requested and allocated in the signaling-only mode ( higher latency of SDCCH compared to TCH, longer time to designate TCH in talk mode if SDCCH has been allocated compared to a channel mode modification procedure while staying on the same TCH channel). In other scenarios, requesting and initial allocation of a TCH in signaling-only mode would be a loss of radio resource if the service, eg location service or supplemental service, can be supported on the SDCCH.
    Moving on to another identified exemplary problem, Figure 4 illustrates a mobile terminating CS call in UTRAN network 78, with the UA 10 in idle mode. In this case, the UA 10 is typically provided with a "paging cause" information in the radio call message sent by the UTRAN network 78, which is information that signals the type of service to which the UA is radio-calling, eg Terminating Conversational Call, Terminating High Priority Signaling, Terminating Low Priority Signaling, as indicated by "paging type 1" 80. This information is forwarded by the RRC protocol in the UA 10 to the upper layers which, by their instead, they request the establishment of the RRC connection and map the cause of the RRC establishment to the received radio call cause, which will be included in the RRC Connection Request 82 sent to the UTRAN network 78.
    However, in the case of the radio call from the UA in E - UTRAN for a CS repair termination session, the radio call (CS service notification) sent by the MME to the UA in connected mode on the source network, packet only (eg , PS) , does not contain any "paging cause" information. This radio call notification may include information about the service to which the mobile station is radio call.
    In case the radio call is made to reach the UA in idle mode, the radio call message sent by the SI interface and on the radio interface does not contain any indication of the service for which the UA is radio called. Furthermore, the upper layers do not specify what information should be passed to the RRC protocol for inclusion in the RRC Connection Request in response to a radio call being placed in the E-UTRAN for the case of the CS recovery procedure. Again, in UTRAN, this could lead to inconsistent UA implementations and result in significantly sub-optimal resource allocations or performance.
    In the case of a mobile originated call in GERAN or UTRAN, the UA includes in the RRC Connection Request channel request sent to the network some additional information, such as the type of channel, cause of establishment, and the like, allowing the network to allocate appropriate resource depending on the service that is requested. Turning now to Figure 5, which is a variation of Figure 2, but showing a data flow for a mobile originated call undergoing CS recovery, the data flow includes operation 24 to deliver a service request from the UA to the network. The service type information element is included in the Extended Service Request message sent to the network. The elements of the type of service information are as follows in Table 2.

    Table 2
    However, this information element does not provide any information to the source network about the requested CS service, which thus does not allow the network to properly size the resources to be allocated according to the requested service and determine the optimal conditions for transferring the UA to the target CS network, for example, depending on available channels and load information, in case inter-RAT handover or cell change order is supported.
    In general, the present system and methods have been developed to reduce the delay and improve the reliability of a CS recovery process. CS recovery could be implemented to pass from E-UTRAN to GERAN, specifically, or more generally, from a first network that does not provide services in the CS domain to a second network that does provide services in the CS domain. For example, CS recovery could be implemented to allow recovery from E-UTRAN networks to GERAN, UTRAN or CDMA2000 networks. To this end, the present system and method facilitates CS recovery by allowing the UA to identify the most appropriate resources to provide the requested service and then request those resources when passing to the CS network during CS recovery. In an implementation of the present system, the UA is configured to analyze the available radio call information received from the network to determine the most appropriate communication channel or radio resource to request for optimal CS recovery performance.
    To initiate CS recovery, the UA may first receive a radio call message from a source PS network (e.g., an E-UTRAN network). The radio call message instructs the UA to implement CS recovery for a CS network (eg, a GERAN network) to access the service. If the related service can be determined using the information carried in the radio call message, the UA is configured to send a channel request message requesting a suitable channel type for that service in the CS network. As such, based on one or more pieces of information contained in the radio call message, the UA is configured to request particular channel types when implementing CS recovery.
    For example, when the radio call message is for a speech call or any call that requires a traffic channel, the UA can be configured to request a 'TCH/H or TCH/F' or a 'TCH' channel /F". Alternatively, when the radio-calling message is to activate an independent supplementary call service, or a location service, for example, the UA may request an SDCCH. In these examples, selecting a channel "TCH/ H or TCH/F" may not require any particular preference for selecting a half-speed (H) or full-speed (F) channel. The network may make the determination of a full-speed or half-speed channel autonomously depending on local conditions (network load status, quality of service (QoS) preferences, etc.) However, the selection of a TCH/F channel may influence the network's decision to select a full or half-speed channel.
    In some circumstances, the radio call message will contain insufficient information for the UA to determine the service for which the UA is radio called. In that case, the UA can be configured to build and send a channel request that reflects a "default" channel type, for example, using the "Any Channel" value or some other indicator that identifies the default channel.
    Thus, in an exemplary implementation of the present system, in the case of a CHANNEL REQUEST triggered by a CS retrieval procedure, such as that described in 3GPP TS 23.272, the content of the CHANNEL REQUEST message can be determined depending on the information that can be derived from the notification radio call received in source radio access technology (RAT) on the service for which the station move1 is radio-calling. If no specific information can be derived from the radio call notification, the content of the CHANNEL REQUEST message can be set to a Paging Indication value that indicates "Any channel". For example, the content of the CHANNEL REQUEST message could be encoded as per Table 3, with the entry "Paging Indication" selected as per the description above to indicate the related service.

    Table 3
    Alternatively, the UA can be configured to select a channel of 'TCH/H or TCH/F', or SDCCH, depending on whether quick set-up or radio resource saving is preferred (preference can be stored as user preferences , or determined by network operator policy, for example) , or some other factor that may require a particular predefined channel.
    Depending on the system implementation, the UA may be configured with an explicit mapping between the service indicated by the radio call message and the type of channel to be requested during recovery. In other cases, however, after determining the service indicated in the radio-call message, the UA may determine the type of channel to request based independently on other information available to the UA. If there is no explicit mapping, and the UA can independently determine the type of channel to be requested, the UA can have more flexibility and can rely on other available pieces of information when identifying the type of channel to request. In contrast, an explicit mapping could prevent different interpretations and ensure consistency in the channel selected by a UA in response to a particular radio call message.
    In an example of the present system, various elements of information present in a CS Service Notification message transmitted between the MME and the UA could be inspected to determine the service for which the UA is radio-called and could therefore allow the UA to request the most appropriate type of channel to provide that service. The elements of information calling line (CLI) supplementary service (SS) Code indicator LCS, and customer identity LCS, for example, may be included within a Message Notification Service CS and their presence or absence may be indicative of the service being requested. Generally, the CLI contains the calling line identification for the mobile termination call in the CS domain that triggered the radio call through SGs. The SS Code information element contains information about the supplementary service transaction in the CS domain that triggered the radio call through SGs. The LCS indicator indicates that the radio call was triggered by an LCS termination request in the CS domain. The LCS client identity contains information related to the requestor of the termination LCS request in the CS domain. Each of the information elements are sent over the network if they are originally received through SGs. Table 4 illustrates the contents of a CS SERVICE NOTIFICATION message.


    These elements of information may be originally received from the MSC Visitor Location Register (VLR) in an SGsAP-PAGING-REQUEST message and passed5 further in the CS SERVICE NOTIFICATION message. The presence or absence of information elements in the SGsAP-PAGING-REQUEST message is governed by several sets of rules and is indicative of the type of service for which CS retrieval is requested. For example, if the radio call is due10 to a network-initiated independent call SS procedure as defined in 3GPP TS 29.002. However, if the radio call is due to a Mobile Terminated Location Request as defined in 3GPP TS 24.030, the VLR may include the LCS client identity and LCS indicator as defined in 3GPP TS 29.002 in the SOsAP-PAGING REQUEST. According to these rules, the various information elements are included in the SGsAP-PAGING REQUEST and are forwarded to the UA in the content of the CS SERVICE message
    NOTIFICATION. As such, the presence or absence of one or more of these information elements allows the UA to determine the service for which the UA is radio-called. Table 5 illustrates an example of the content of the SGsAP-PAGING REQUEST message10.

    Table 5
    As shown in Table 5, the SS code is included if the radio call is due to a network-initiated Call Independent SS procedure (see 3GPP TS 24.010). 0 5 LCS indicator is included if the radio call is due to a Mobile Terminated Location Request (see 3GPP TS 24.030). The LCS client identity is included if the radio call is due to a Mobile Terminated Location Request (see 3GPP TS 24.030). The required channel information element 10 is included if the VLR wants to indicate which channel the UA should use.
    The UA may further be configured to inspect additional information to determine the services indicated by a particular radio call request. Additional information may include other elements of information that may be added in the future, including those identified below.
    The present system may also be configured to include information related to the service available in the MME in radio-calling messages used to radio-calling the UE in idle mode. For example, service-related information may be added to SI and RRC radio call messages. In one example, service-related information may include the information elements "SS Code", "LCS indicator" and "LCS client identity" described above. Service-related information may be communicated to the MME by the MSC/VLR over the SGs interface in the SGsAP-PAGING-REQUEST message. In some cases, these information elements are already present in the CS Service Notification message used to radio-call the UA in connected mode and, therefore, can be added to the SI Interface Paging message of the SI Interface by the MME and to the Paging message of the Service Interface. E-UTRAN radio RRC by E-UTRAN RRC protocol. The additional information presented in the radio call messages can then be used when the UA is radio called in idle mode in addition to the case where the UA is radio called in connected mode.
    Table 6 illustrates an SI interface radio call message that is modified to include the SS Code, LCS indicator, and CLS client identity information elements.

    Table 6
    Table 7 illustrates an E-UTRAN RCC protocol radio call message that is modified to include the SS Code, LCS indicator, and LCS 5 client identity information elements.

    Table 7
    Referring to Table 7, the SS-Code carries information related to a network-initiated supplementary service request. The lcs-lindicator indicates that the origin of the message is due to an LCS request and the type of the request. The encoding of the les-indicator is given by the value part of the information element of the LCS indicator in TS 24.301. les-Client-Identity takes client-related information from an LCS request. The encoding of the LCS client identity is given in sub-clause 17.7.3 of 3GPP TS 29.002.
    Figure 6 is an illustration of a message flow for implementing CS retrieval in which service-related information is passed to the UA 10 within a radio call message. In steps 100, 102 and 104 a call terminated by the UA arrives at MSC/VLR 140. In step 106, an SGsAP-Paging-Request message is transmitted to the MME 20. The SGsAP-Paging-Request may include one or more elements information indicative of the type of service requested. In steps 108 and 110 the MME 20 forwards a radio call message to the UA 10. The radio call message is modified to include one or more of the information elements described above. The present or absence of one or more of the information elements allows the UA to identify the type of service for which the radio call message is sent. As a result, in step 112, the UA may request an appropriate resource for the service. In step 114, in response to the service request, the MME 20 issues an initial UA context establishment message. In steps 116, 118 and 120, the PS handover or, alternatively, a base station aided cell change or an RRC release with redirect, possibly followed by a location area update is completed. In step 122, the radio call response is transmitted to the RNC/BSC 142 of the UA 10 and the radio call response is forwarded to the MSC/VLR 140 in step 124. If the MSC is not changed, the CS connection is established in step 126 and the CS recovery process is complete. If, however, the MSC is changed, in step 128 the MSC/VLR 140 transmits a connection rejection to the RNC/BSC 142. In response, the RNC/BSC 142 transmits a signaling connection release to the UA 10 at step 130. At this point, an update of the location area and retry travel (roaming) is initiated to attempt CS recovery in step 132.
    Alternatively, to facilitate CS retrieval, a Channel Needed information element, when known to the MME, may be added to the radio call messages sent to the UA to radio call the UA in idle mode or connected mode. For example, a Channel Needed information element could be added to the CS Service Notification NAS message (described above) transmitted between the MME and the UA, the SI Interface Paging message described above, or the RRC radio interface protocol described above. In some cases, the data used to populate the Channel Needed information element is communicated to the MME by the MSC/VLR over the SGs interface in the SGsAP-PAGING-REQUEST message, as described above. The Channel Needed information, when present within a radio call message, allows the UA to efficiently create an appropriate channel request message when the UA responds to the CS recovery radio call in GERAN, as the same information would be present. as in the GERAN radio call message (if transmitted by the MSC/VLR).
    To allow the UA radio-call in the E-UTRAN for a Mobile Terminating CS Call with recovery to send the appropriate cause of establishment when responding in a UTRAN network, new mapping entries may be introduced. This would allow the UA to communicate to the network the appropriate set-up causes, effecting the service for which the UA is radio-calling, if the related service can be evaluated from the information carried in the radio-calling message. In that case, the UA, when responding in UTRAN to a radio call received in the target packet network (for example, E-UTRAN), may include the mapped establishment cause communicated by the higher layers in the RRC Connection Request message.
    As an example, the cause of the establishment could be determined as follows. The cause of establishment may be "Terminating Conversational Call" when the incoming radio call is for a speech call or any other CS conversational call or "Terminating 10 High Priority Signalling" when the incoming radio call is for activating a supplementary service independent of call, or a location service.
    If the service for which the UA is radio-called cannot be evaluated from the information available from the network, the UA may use "Terminating - cause Unknown" as the cause of establishment.
    Table 8 illustrates an exemplary mapping of the CS NAS procedure for establishing cause.

    Table 8
    Various information elements, when present in a CS Service Notification message between the MME and the UA, may provide an indication of the service for which the mobile is radio-called, including the information elements "SS Code", "LCS indicator" and "LCS client identity". The various pieces of information may be received from the MSC/VLR in an SGsAP-PAGING-REQUEST message as described above. The presence or absence of one or more of these information elements, therefore, may allow the UA to make the determination of the service to which the UA is radio-called. Any other information that can be accessed or retrieved by the UA from messages received from the network or other sources may be used to determine the service for which the UA is radio-called. This may include new information elements added in the future, including those described above.
    Upon initiation of a Mobile Originating (MO) call, the UA may be configured to provide additional information to the PS network describing the requested CS service for which CS retrieval may be triggered. In one implementation, the UA includes additional information in the Extended Service Request message transmitted to the PS network MME describing the CS service being requested. Similarly, additional information may be included in an INITIAL CONTEXT SETUP REQUEST, or UA CONTEXT MODIFICATION REQUEST message transmitted from the MME to the eNodeB using the SI interface (see 3GPP TS 36.413).
    Table 9 and Table 10 illustrate a modified Extended Service Request message that includes additional information describing the CS service requested by a UA initiating the MO call resulting in CS recovery.

    As shown in Table 9 and Table 10, the Extended Service Request message shown in Table 9 includes an additional element called "Extended service request cause". The extended service request cause information element detail is shown in Table 10. The extended service request cause element is configured to store an identifier value in octet 1 that describes the requested CS service. For example, the identifier may be used to refer to CS services as Originating Conversational Call, Originating High Priority Signalling, or Originating Low Priority Signalling. Table 11 illustrates an exemplary configuration of octet 1 of the information element cause of extended service request.
    Table 11
    In some cases, the existing service type information element present within existing Extended Service Request messages may be modified and used to identify the CS service being requested. Alternatively, additional information elements indicating the originating service, such as "SS Code" or "LCS indicator" defined for the Service Notification message may be included in the message when the UA initiates a Mobile Originating call. In another example, the CS service information could be included in the RRCConnectionRequest message (see 3GPP TS 36.331) which could be used to switch the UA from idle mode to connected mode when initiating a Mobile Originating call undergoing CS retrieval.
    Figure 7 shows an exemplary block diagram of the UA 10. Although a variety of known UA 10 components are depicted, in one release, a subset of the related components and/or additional unrelated components may be included in the UA 10. 0 The UA 10 includes a processor such as a digital signal processor (DSP) 802, and a memory 804. As shown, the UA 10 may further include an antenna and a front end unit 806 and a radio frequency (RF) transceiver 808 , and an analog baseband processing unit 810. In various configurations, the UA 10 may include optional additional components as illustrated in Figure 7. Additional components may, for example, include a microphone 812, an in-ear speaker 814 , a headphone port 816, an input/output interface 818, a removable memory card 820, a universal serial bus (USB) port 822, a wireless communication subsystem. short range 824, an alert 826, a keyboard 828, a liquid crystal display (LCD) that may include a touch-sensitive surface 830, an LCD controller 832, a charge-coupled camera device (CCD) 834, a controller camera 836, and a global positioning sensor system (GPS) 838. In one version, the UA 10 may include another type of monitor that does not provide a touchscreen. In one version, the DSP 802 will be able to communicate directly with the 804 memory without going through the 818 I/O interface.
    The DSWP 802 or some other form of controller or central processing unit operates to control the various components of the UA 10 in accordance with embedded software or firmware stored in 804 memory or made available through information-carrying media such as portable data storage media. such as the 820 removable memory card or via wired or wireless network communication. Application software may comprise a compiled set of machine read instructions that configure the DSP 802 to provide the desired functionality, or application software may high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 802.
    The antenna and front end unit 806 may be provided to convert wireless signals to electrical signals, allowing the UA 10 to send and receive information from a cellular network or some other available wireless communication network or from a UA 10 pair. In one version, the antenna and front end unit 806 may include multiple antennas to support beamforming and/or multiple input and multiple output (MIMO) operations. As is known to those skilled in the technology, MIMO operations will be able to provide spatial diversity that can be utilized to overcome difficult channel conditions and/or increase channel productivity. The antenna and front end unit 806 may include antenna tuning and/or impedance matching components, RF energy amplifiers and/or low noise amplifiers.
    The 808 RF transceiver provides frequency shifting, converting the received RF signals to baseband and converting the transmission signals from baseband to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, encoding/decoding, interlacing/deinterlacing, scattering/descattering, inverse fast Fourier transform (IFFT)/Fourier transform fast (FFT), cyclic prefix append/remove, and other signal processing functions. For the sake of clarity, the description presented here separates the description of this RF and/or radio stage signal processing and conceptually allocates this signal processing to the analog baseband processing unit 810 and/or the DSP 802 or other signal processing unit. central processing. In some versions, the RF transceiver 808, antenna and front end portions 806, and the analog baseband processing unit 810 may be combined into one or more processing units and/or application-specific integrated circuits (ASICs). Analog baseband processing unit 810 may provide various analog processing of inputs and outputs, for example, analog processing of inputs from microphone 812 and ear set 816 and outputs to headset 814 and ear set 816.
    The DSP 802 can perform modulation/demodulation, encoding/decoding, interlacing/deinterlacing, scattering/descattering, inverse fast Fourier transform (IFFT)/fast Fourier TRANSFORM (FFT), cyclic prefix appending/removal, and other functions signal processing associated with wireless communications. In one version, in an application of code division multiple access (CDMA), for a transmitting function the DSP 802 can perform modulation, encoding, interlacing, and spreading, and for the receiving function the DSP 802 can perform removal of cyclic prefix, fast Fourier transform, deinterlacing, decoding, and demodulation. In other wireless technology applications, still other signal processing functions and combinations of signal processing functions can be performed by the DSP 802. The DSP 802 can communicate with a wireless network through the analog baseband processing unit 810 .
    Figure 8 illustrates a 902 software environment that may be implemented by a UA 10 processor or controller. The 902 software environment includes 904 operating system drivers that are run by the UA 10 processor or controller to provide a platform from which the rest of the software operates. The 904 operating system triggers provide triggers to the UA hardware with standardized interfaces that are accessible to application software. Operating system triggers 904 include application management services ("MAS") 906 that transfer control between applications that process in the UA 10. Also shown in Figure 8 is a web browser application 908, a media player application. 910, and Java applets 912.
    The UA 10 includes a processing component like the DSP that is capable of executing instructions related to the actions described above. Figure 9 illustrates an example of a system 1000 that includes one or more of the components that provide the functionality of the UA 10. The system 1000 includes a processing component 1010 suitable for implementing one or more of the versions described herein. In addition to the 1010 processor (which may be referred to as a central processor unit (CPU or DSP), the system 1000 may include 1020 network connectivity devices/random access memory (RAM) 1030, read-only memory (ROM) 1040 , secondary storage 1050, and input/output (I/O) devices 1060. In some cases, some of these components may not be present or may be combined in various combinations with each other or with other components not shown. described as being taken by processor 1010 may be taken by processor 1010 alone or by processor 1010 in conjunction with one or more of the components shown or not shown in the drawing.
    The 1010 processor executes instructions, code, computer programs, or scripts that it can access from network connectivity devices 1020, RAM 1030, ROM 1040, or secondary storage 1050 (which can include multiple disk-based systems such as hard disk, floppy disk, or optical disk). Although only one 1010 processor is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by one processor, instructions may be executed simultaneously, serially, or otherwise by one or multiple processors. The 1010 processor may be implemented as one or more CPU chips.
    The 1020 network connectivity devices may include one or more 1025 transceiver components capable of wirelessly transmitting and/or receiving data in the form of electromagnetic waves, such as radio frequency signals or microwave frequency signals. Transceiver component 1025 may include separate receiving and transmitting units or a single transceiver. Information transmitted or received by transceiver 1025 may include data that has been processed by processor 1010 or instructions that must be executed by processor 1010. Such information may be received from and outputted to a network in the form, for example, of a baseband signal. computer data or signal embedded in a carrier wave. The data may be ordered according to different sequences as may be desirable either for processing or for generating the data or transmitting or receiving the data. The baseband signal, the signal embodied in the carrier wave, or other types of signals currently used or hereinafter developed may be referred to as the transmission medium and may be generated according to various methods well known to one skilled in the art. technology.
    The RAM 1030 can be used to store volatile data and perhaps to store instructions that are executed by the processor 1010. The ROM 1040 is a non-volatile memory device that typically has a memory capacity less than the memory capacity of the storage. secondary 1050. The ROM 1040 can be used to store instructions and perhaps data that is read during the execution of instructions. Accessing both RAM 103 0 and ROM 104 0 is typically faster than for secondary storage 1050.
    1060 I/O devices may include liquid crystal displays (LCDs), touch screens, keyboards, key pads, switches, buttons, mouse, scroll balls, voice recognizers, card readers, paper strip readers , printers, video monitors, or other well-known input/output devices. Also, the 1025 transceiver can be considered to be a component of the 1060 I/O devices instead of or in addition to being a component of the 1020 network connectivity devices. Some or all of the 1060 I/O devices may be substantially similar to the various components depicted in the above-described drawing of the UA 10, such as screen 702 and input 704.
    Although various versions have been provided in the present disclosure, it is to be understood that the systems and methods disclosed may be incorporated in many other specific forms without departing from the spirit and/or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and are not intended to be limited to the details provided herein. For example, various elements or components may be combined or integrated into another system, or certain features may be omitted or not implemented.
    Furthermore, techniques, systems, subsystems, and methods described herein and illustrated in the various versions as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions and alterations are verifiable by someone skilled in the technology and can be done without deviating from the spirit and scope revealed here.
    To inform the public of the scope of this disclosure, the following claims are made.
    权利要求:
    Claims (10)
    [0001]
    1. Method implemented by a wireless device (10) for circuit-switched (CS) recovery from a first network (12) that does not provide circuit-switched domain service (CS domain), the method characterized in that it comprises : receiving from the first network (12) a radio call message (72) for circuit-switched retrieval to a circuit-switched network (14, 74, 78); radio call message (72); transmitting a request message (76) to initiate establishment of a circuit switched radio connection, the request message (76) identifying the appropriate channel type; and use the service in the circuit switched network (14, 74, 78).
    [0002]
    2. Method according to claim 1, characterized in that the service is one of a first category of service, the first category of service including CS speech calls and CS services that require a traffic channel or conversational resources, a second category of service, the second category of service including mobile terminated location requests or a third category of service, the third category of service including supplementary services.
    [0003]
    3. Method according to claim 2, characterized in that if the service is in the first category of service, the type of channel suitable for the service is at least one of a half-rate traffic channel (TCH/H) or a full rate traffic channel (TCH/F).
    [0004]
    4. Method according to claim 2, characterized in that if the service is in at least one of the second or third service categories, the appropriate channel type for the service is an individualized dedicated control channel (SDCCH) .
    [0005]
    5. Method according to claim 1 or 2, characterized in that when the service is undefined, the appropriate channel type for the service is determined as a default channel.
    [0006]
    6. Method according to any one of claims 1 to 5, characterized in that the determination comprises: detecting at least one of a supplementary service code (SS) information element, a location service indicator element ( LCS), and an LCS client identity information element within the radio call message (72); and wherein when the radio call message (72) includes the SS code information element, the appropriate channel type for the service is selected for a call-independent supplementary service; and when the radio call message (72) includes at least one of the LCS indicator information element and the LCS client identity information element, the appropriate channel type for the service is selected for a mobile terminated location request.
    [0007]
    7. Method according to any one of claims 1 to 6, characterized in that the radio call message (72) includes a CS SERVICE NOTIFICATION message.
    [0008]
    8. Method according to any one of claims 1 to 7, characterized in that the radio call message (72) includes an E-UTRAN RRC protocol radio call message received after a radio call procedure preliminary implemented using an S1 interface.
    [0009]
    9. Wireless mobile communication device (10), characterized in that it is adapted to perform the method as defined in any one of claims 1 to 8.
    [0010]
    10. A computer-readable medium comprising computer-executable instructions, characterized in that the instructions are for performing method 15 as defined in any one of claims 1 to 8.
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012010965B1|2021-08-03|METHOD, DEVICE AND COMPUTER-READABLE MEANS FOR DETERMINING THE RADIO RESOURCE TO BE REQUESTED IN THE EVENT OF A SWITCHED FAULT RECOVERY PROCEDURE
    AU2018366776B2|2021-07-01|Session establishing method and device
    BR122020015813B1|2021-01-12|method for user equipment to establish a voice service, and user equipment
    KR20120095897A|2012-08-29|Method and system to support single radio video call continuity during handover
    CN103607783B|2017-04-26|CSFB | call establishment method and user equipment
    RU2715725C1|2020-03-03|Wireless device serving transmission systems and methods
    US10477467B2|2019-11-12|Method and system for handling voice and non-voice calls in a CSFB scenario
    CN110366214B|2021-06-15|Network switching method and device for voice service
    US20140094174A1|2014-04-03|Controlling handover of a mobile station from e-utran to utran/geran circuit switched in a multi-operator core network
    WO2015062468A1|2015-05-07|Method, device and system for single radio voice call continuity handover
    CN107079274B|2020-06-09|Emergency call handling using over-the-top services
    EP3704850A1|2020-09-09|Method and function for handling traffic for an application
    WO2018195907A1|2018-11-01|Wireless communication method, network device, and terminal device
    WO2022007484A1|2022-01-13|Redirection method, network device, terminal device, and readable storage medium
    WO2016045029A1|2016-03-31|Circuit-switching service processing method and terminal
    WO2019097498A1|2019-05-23|Methods and apparatus for handover or redirection
    WO2015070425A1|2015-05-21|Circuit switched fall back user device identification method and device
    US20210321356A1|2021-10-14|Method, apparatus, and computer program product for expediting an emergency services initiation
    WO2021196171A1|2021-10-07|Network slice handover method and apparatus, and device therefor
    WO2015184865A1|2015-12-10|Method and system for recognizing circuit switched fallback service
    WO2016029479A1|2016-03-03|Voice service bearer switching method, relevant apparatus and system
    WO2018082039A1|2018-05-11|Method, device and system of signaling transmission
    WO2014180511A1|2014-11-13|Method and apparatuses handling control relocation failures
    同族专利:
    公开号 | 公开日
    WO2011054089A1|2011-05-12|
    CA2779737A1|2011-05-12|
    US20110110302A1|2011-05-12|
    EP2506632A1|2012-10-03|
    EP2320698B1|2012-07-04|
    HK1173600A1|2013-05-16|
    US10172045B2|2019-01-01|
    US20170195923A1|2017-07-06|
    US8929310B2|2015-01-06|
    KR101445460B1|2014-09-26|
    KR20120085857A|2012-08-01|
    CN102598845A|2012-07-18|
    US9532274B2|2016-12-27|
    BR112012010965A2|2016-04-12|
    ES2390813T3|2012-11-16|
    EP2506632B1|2016-08-17|
    CN102598845B|2015-03-11|
    JP2013510471A|2013-03-21|
    CA2779737C|2017-01-17|
    JP5520386B2|2014-06-11|
    EP2320698A1|2011-05-11|
    US20150071252A1|2015-03-12|
    US20120014345A1|2012-01-19|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US6314292B1|1997-08-15|2001-11-06|Nortel Networks Limited|Method and apparatus for enhanced call setup|
    US6292664B1|1998-02-06|2001-09-18|Telefon Aktiebolaget Lm Ericsson |Channel quality in wireless communications|
    US20020128002A1|1998-11-13|2002-09-12|Trinh D. Vu|Wireless communication unit programming|
    CN101151936B|2005-03-30|2013-04-24|诺基亚公司|Switch method|
    US20060268781A1|2005-05-02|2006-11-30|Telefonaktiebolaget Lm Ericsson |System and method for call handoff from packet data wireless network to circuit switched wireless network|
    US9154907B2|2005-06-21|2015-10-06|Qualcomm Incorporated|Efficient periodic location reporting in a radio access network|
    KR101233150B1|2005-07-19|2013-02-15|엘지전자 주식회사|Method for Setup and Controlling Service Connection|
    US9420612B2|2005-08-19|2016-08-16|Core Wireless Licensing S.A.R.L.|Apparatus, method and computer program product providing simultaneous radio resource and service requests|
    WO2008026094A1|2006-08-28|2008-03-06|Nokia Corporation|Method, system and terminal for multimedia session establishment|
    US8159980B2|2006-10-03|2012-04-17|Nokia Corporation|PS network with CS service enabling functionality|
    FI20065866A0|2006-12-29|2006-12-29|Nokia Corp|Data transmission in a mobile communication system|
    EP1983789A1|2007-04-17|2008-10-22|Nokia Siemens Networks Oy|Service redirection in evolved communication systems|
    CN101731016B|2007-06-08|2012-11-21|Lm爱立信电话有限公司|Circuit switched fallback mechanism|
    US8259673B2|2007-06-19|2012-09-04|Telefonaktiebolaget L M Ericsson |System and method for providing voice service in a mobile network with multiple wireless technologies|
    US20090042576A1|2007-07-27|2009-02-12|Interdigital Patent Holdings, Inc.|Method and apparatus for handling mobility between non-3gpp to 3gpp networks|
    CN101374333A|2007-08-23|2009-02-25|华为技术有限公司|System, apparatus and method for switching user service|
    ES2647943T3|2007-12-06|2017-12-27|Telefonaktiebolaget Lm Ericsson |Method for updating UE capacity information in a mobile telecommunications network|
    WO2009071702A1|2007-12-07|2009-06-11|Telefonaktiebolaget Lm Ericsson |Domain transfer service continuity provision to a mobile terminal|
    CN101222765B|2008-01-24|2012-06-06|中兴通讯股份有限公司|Control method, system and device for circuit field fall-back|
    CN101499967B|2008-02-03|2011-07-13|中兴通讯股份有限公司|Circuit domain call implementing method and system|
    AT543355T|2008-05-19|2012-02-15|Ericsson Telefon Ab L M|LINE-CONTROLLED FALLBACK IN A DEVELOPED PACKAGE SYSTEM|
    US8243725B2|2008-08-13|2012-08-14|Interdigital Patent Holdings, Inc.|Maintaining circuit switched continuity in an enhanced universal terrestrial radio access network|
    WO2010120689A2|2009-04-14|2010-10-21|Interdigital Patent Holdings, Inc.|Method and apparatus for processing emergency calls|
    WO2011038352A1|2009-09-26|2011-03-31|Cisco Technology, Inc.|Providing offloads in a communication network|US8223938B2|2005-09-30|2012-07-17|At&T Intellectual Property I, L.P.|Methods, systems, and computer program products for providing caller identification services|
    US20070209054A1|2005-09-30|2007-09-06|Bellsouth Intellectual Property Corporation|Methods, systems, and computer program products for providing communications services|
    US8804695B2|2005-09-30|2014-08-12|At&T Intellectual Property I, L.P.|Methods, systems, and computer program products for providing alerts and notifications|
    US8654724B2|2009-01-29|2014-02-18|Panasonic Corporation|Base station apparatus, mobile station apparatus, and transmission method|
    EP2309810A1|2009-10-08|2011-04-13|Thomson Telecom Belgium|Method for checking the presence of a mobile device in a cell|
    CN102158907B|2010-02-12|2013-01-23|华为技术有限公司|Priority service processing method, device and system|
    US9277449B2|2010-04-19|2016-03-01|Htc Corporation|Method of load balancing and related communication device|
    US20110299429A1|2010-06-02|2011-12-08|Kundan Tiwari|Methods for handling ps and cs communication service|
    CN102378250B|2010-08-23|2015-08-12|中兴通讯股份有限公司|A kind of processing method of priority business and system|
    WO2012064076A2|2010-11-08|2012-05-18|엘지전자 주식회사|Rrc connection method and device therefor in wireless communication system|
    TWI533629B|2010-12-28|2016-05-11|內數位專利控股公司|Triggering devices that are not attached to a wireless network|
    US8655305B2|2011-03-21|2014-02-18|Htc Corporation|Methods for requesting emergency bearer services for low priority devices, and apparatuses using the same|
    CN102833807B|2011-06-14|2015-05-27|华为技术有限公司|Method and device for suspending packet data service|
    JP2013009169A|2011-06-24|2013-01-10|Kyocera Corp|Radio terminal device and communication control method|
    JP5848062B2|2011-08-24|2016-01-27|株式会社Ｎｔｔドコモ|Base station and system information notification method|
    US9961591B2|2011-10-18|2018-05-01|Qualcomm Incorported|Optimizations to circuit-switched fallbackprocedure|
    EP2836015A4|2012-04-03|2016-01-27|Lg Electronics Inc|Method and device for handover of packet switched service in wireless communication system|
    US9078109B2|2012-04-09|2015-07-07|Intel Corporation|Frame structure design for new carrier type |
    US9641297B2|2012-04-09|2017-05-02|Intel Corporation|Enhancements to wireless networks to support short message servicecommunication in the packet switched domain|
    US9125122B2|2012-06-09|2015-09-01|Apple Inc.|Paging for circuit switched fallbackin long term evolutionconnected mode|
    CN103517414A|2012-06-26|2014-01-15|中兴通讯股份有限公司|Method and apparatus for paging of machine type communication user equipment|
    CN104380818B|2012-06-28|2019-01-29|苹果公司|The method, apparatus and wireless telecom equipment made a response to paging message|
    US9049634B2|2012-09-18|2015-06-02|Acer Incorporated|Apparatuses and methods for camping back to LTE-based network after finishing CSFB call with non-LTE network|
    US9232531B2|2012-10-22|2016-01-05|Qualcomm Incorporated|Prioritization of users for switching between co-existence wireless systems|
    US8874069B1|2012-11-19|2014-10-28|Sprint Spectrum L.P.|Dynamically toggling data dedicated transmission mode in a wireless communication device|
    US8824374B2|2012-12-20|2014-09-02|Alcatel Lucent|Call setup latency optimization for LTE to 1xRTT circuit switched fall back|
    EP2925081B1|2012-12-28|2017-09-06|Huawei Technologies Co., Ltd.|Circuit switched fall back switching method, device and base station|
    CN103916920B|2012-12-31|2017-04-26|展讯通信（上海）有限公司|Method and system for processing paging|
    US10142890B2|2013-01-04|2018-11-27|Samsung Electronics Co., Ltd.|Method and system to minimize delay in circuit-switched fallbackprocedure|
    JP5525092B1|2013-04-05|2014-06-18|日本電気株式会社|Mobility management device, communication system, voice incoming call control method, and program|
    CN104113388B|2013-04-19|2017-06-20|中国移动通信集团公司|The determination method and device of business control signaling expense|
    CN103858484B|2013-06-14|2017-12-05|华为技术有限公司|A kind of CSFB implementation methods and equipment|
    US20140370835A1|2013-06-14|2014-12-18|Htc Corporation|Method of Handling Radio Resource Control Connection Establishment during Reception of Public Warning System Message in Wireless Communication System and Communication Device Thereof|
    US9730152B2|2013-09-27|2017-08-08|Mediatek Inc.|UE enhancement in FDD-TDD joint operation networks|
    WO2015126160A1|2014-02-20|2015-08-27|Samsung Electronics Co., Ltd.|Video telephony service quality enhancement method and apparatus|
    USD760601S1|2014-08-04|2016-07-05|Duet Bottle Company, LLC|Double-ended bottle|
    EP3205123B1|2014-10-07|2020-04-22|Telefonaktiebolaget LM Ericsson |Paging procedure for a wireless device, a radio access node, methods performed therein, a computer program, and a computer-readable storage medium|
    US9756088B2|2015-09-08|2017-09-05|Qualcomm Incorporated|IMS over soft AP admission control and resource management|
    EP3347583B1|2015-09-11|2020-11-25|Volvo Truck Corporation|Powertrain arrangement and method for use with additized dimethyl etherfuel|
    CN109246720B|2017-05-11|2021-04-09|电信科学技术研究院|Method and terminal for determining establishment cause|
    US11057904B2|2017-12-06|2021-07-06|T-Mobile Usa, Inc.|Prioritization of mobile terminating radio resource control connections|
    US10757602B2|2018-12-07|2020-08-25|Ford Global Technologies, Llc|Connection history-based retry throttling|
    US10904938B2|2019-03-12|2021-01-26|Ford Global Technologies, Llc|Circuit-switched domain response to packet-switched domain failure|
    CN113556829A|2020-04-23|2021-10-26|维沃移动通信有限公司|Method for establishing network connection and electronic equipment|
    法律状态:
    2018-03-20| B25D| Requested change of name of applicant approved|Owner name: BLACKBERRY LIMITED (CA) |
    2018-04-10| B25G| Requested change of headquarter approved|Owner name: BLACKBERRY LIMITED (CA) |
    2019-01-08| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-02-11| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2020-02-18| B15K| Others concerning applications: alteration of classification|Free format text: AS CLASSIFICACOES ANTERIORES ERAM: H04W 88/06 , H04W 68/00 Ipc: H04W 36/00 (2009.01), H04W 68/12 (2009.01), H04W 7 |
    2021-06-08| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-07-27| B09W| Decision of grant: rectification|Free format text: POR INCORRECAO NA REIVINDCACAO DEPENDENTE 2. |
    2021-08-03| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 08/11/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF, QUE DETERMINA A ALTERACAO DO PRAZO DE CONCESSAO. |
    优先权:
    申请号 | 申请日 | 专利标题
    EP09306075.4|2009-11-09|
    EP09306075A|EP2320698B1|2009-11-09|2009-11-09|Determination of a channel type to be requested in case of a circuit-switched fallback procedure|
    PCT/CA2010/001739|WO2011054089A1|2009-11-09|2010-11-08|Determination of appropriate radio resource to be requested in case of a circuit-switchedfallback procedure|
    [返回顶部]